Method and nodes for handling a user equipment&#39;s access to a mobile communications network

ABSTRACT

The embodiments herein relate to a method in a policy node for handling a UEs access to a mobile communications network. The policy node comprises policy information for the UEs access rights to the mobile communications network. The policy node obtains, from a subscriber database, subscription information for a subscriber associated with the UE. Based on the subscription information and the policy information, the policy node determines which geographical areas comprised in the mobile communications network the UE is allowed or denied access to. The policy node transmits, to a mobility node, access information indicating which geographical areas comprised in the mobile communications network the UE is allowed or denied access to.

This application is a 35 U.S.C. § 371 national phase filing ofInternational Application No. PCT/EP2015/051719, filed Jan. 28, 2015,the disclosure of which is incorporated herein by reference in itsentirety.

TECHNICAL FIELD

Embodiments herein relate generally to a policy node, a method in thepolicy node, a mobility node and a method in the mobility node. Moreparticularly the embodiments herein relate to handling a UserEquipment's (UE) access to a mobile communications network.

BACKGROUND

PCC Architecture

Policy and Charging Control (PCC) was originally introduced in ThirdGeneration Partnership Project (3GPP) standards as a mean to secureresources in the access network mainly for dynamic services (such asInternet protocol based Multimedia Services (IMS)), but also to controlresource consumption for regular Internet services (e.g. Point to Point(P2P) traffic, web-browsing, File Transfer Protocol (FTP) etc.) and toenable Flow Based Charging (FBC). Although the original goal with PCChas since long time been completed in the 3GPP, there is still a lot ofactivities ongoing in standards enhancing the PCC framework withadd-ons.

An example embodiment of an architecture that supports the PCCfunctionality is depicted in FIG. 1. The PCC functionality illustratedin FIG. 1 is for an Evolved 3GPP Packet Switched (PS) domain, includingboth 3GPP accesses and Non-3GPP accesses. Some examples of 3GPP accessare GSM EDGE Radio Access Network (GERAN), Universal Terrestrial RadioAccess Network (UTRAN) and Evolved UTRAN (E-UTRAN). GSM is short forGlobal System for Mobile Communications and EDGE is short for EnhancedData rates for GSM Evolution.

The Policy Control and Charging Rules Function (PCRF) 101 in FIG. 1 is afunctional element or node that encompasses policy control decision andflow based charging control functionalities. Policy control may bedescribed as the process where the PCRF 101 indicates to a Policy andCharging Enforcement Function (PCEF) 102 how to control the InternetProtocol-Connectivity Access Network (IP-CAN) bearer. The PCRF 101provides network control regarding the service data flow detection,gating, Quality of Service (QoS), Application Detection and Control(ADC) and flow based charging (except credit management) towards thePCEF 102. The PCRF 101 receives session and media related informationfrom the Application Function (AF) 103 and informs the AF 103 of trafficplane events. The PCRF 101 also receives information about services inuse from a Traffic Detection Function (TDF) 105 and informs the TDF 105about IP-CAN session specific information. An IP-CAN session may bedescribed as an association between a UE and an Internet Protocol (IP)network.

The PCRF 101 may provision PCC Rules and ADC to the PCEF 102 via the Gxreference point. The PCRF 101 may provision ADC Rules to the TDF 105 viathe Sd reference point.

The PCRF 101 may inform the PCEF 102 and the TDF 105 through the use ofPCC and ADC rules on the treatment of each service data flow that isunder PCC/ADC control, in accordance with the PCRF 101 policydecision(s).

The AF 103 is node or an element offering applications in which serviceis delivered in a different layer (i.e. transport layer) from the onewhere the service has requested the control of IP bearer resourcesaccording to what has been negotiated (i.e. signaling layer). Oneexample of an AF 103 is the Proxy-Call Session Control Function (P-CSCF)of the IP Multimedia Core Network (IM CN) subsystem. The AF 103 maycommunicate with the PCRF 101 to transfer dynamic session information(i.e. description of the media to be delivered in the transport layer).This communication is performed using the Rx interface.

The PCEF 102 encompasses service data flow detection (based on thefilter definitions included in the PCC and ADC rules), as well as onlineand offline charging interactions (not described here) and policyenforcement. Since the PCEF 102 is the entity handling the bearers it iswhere the QoS is being enforced for the bearer according to the QoSinformation coming from the PCRF 101. This functional entity may belocated at a Gateway 108 (e.g. Gateway GPRS Support Node (GGSN) in theGeneral Packet Radio Services (GPRS) case, and Packet DataNetwork-GateWay (PDN-GW) in the Evolved Packet System (EPS) case). Forthe cases where there is Proxy Mobile IPv6 (PMIP) instead of GPRSTunneling protocol (GTP) protocol between the Bearer Binding and EventReporting Function (BBERF) 110 and PCEF 102, the bearer control is donein the BBERF 110 instead.

The BBERF 110 may be described as a node which performs e.g. bearerbinding, uplink bearer binding verification, event reporting to the PCRF101, sending or receiving IP CAN-specific parameters, to or from thePCRF 101 etc. The Gxx reference point resides between the PCRF 101 andthe BBERF 110.

The Subscription Profile Repository (SPR) 113 is an entity, e.g. alogical entity, which comprises substantially allsubscriber/subscription related information needed forsubscription-based policies and IP-CAN bearer level PCC rules by thePCRF 101. The SPR 113 may be combined with or distributed across otherdatabases in the operator's network. The Sp reference point lies betweenthe SPR 113 and the PCRF 101.

The Online Charging System (OCS) 115 is a node which performs onlinecredit control functions. The OCS 115 may trigger the PCEF 102 toinitiate an IP-CAN bearer service termination at any point in time. TheSy reference point resides between the PCRF 101 and the OCS 115. The Gyreference point resides between the OCS 115 and the PCEF 102. The Gynreference point resides between the OCS 115 and the TDF 105.

There may be several Offline Charging Systems (OFCS) 118 in a PublicLand Mobile Network (PLMN). The default OFCS 118 addresses (i.e. theprimary address and the secondary address) may be locally pre-configuredwithin the PCEF 102 and the TDF 105. OFCS 118 addresses may also bepassed once per IP-CAN session or TDF 105 session from the PCRF 101 tothe PCEF 102 or TDF 105. The addresses provided by the PCRF 101 may havea higher priority than the pre-configured ones. The Gzn reference pointresides between the TDF 105 and the OFCS 118. The Gz reference pointresides between the PCEF 102 and the OFCS 118.

MME/SGSN-PCRF Interface

The MME/SGSN-PCRF reference point is a reference point which residesbetween the MME/SGSN and the PCRF. MME is short for Mobility ManagementEntity and SGSN is short for Serving GPRS Support Node. The SGSN mayalso be referred to as a S4-SGSN. The reference point may also bereferred to as an interface. The MME/SGSN may be referred to as amobility node and may comprise the functions of the MME and the SGSN,i.e. the MME and the SGSN may be co-located in one node. The MME/SGSNprovides packet-data switching and mobility/session management.

The MME/SGSN-PCRF interface is initiated by the MME/SGSN e.g. duringInitial Attach, Packet Data Protocol (PDP)-context activation prior tosending a Crete Session Request message towards the Serving GateWay(SGW) from the MME/SGSN. The MME/SGSN-PCRF interface may also beinitiated by a new MME/SGSN during applicable EPS/GPRS procedures whenthere is a MME/SGSN change (e.g. during a Tracking Area Update (TAU) andRouting Area Update (RAU) with a MME/SGSN change).

The MME/SGSN-PCRF interface may be session based, i.e. stateful, perPacket Data Network (PDN) connection or per PDP context. The PCRF maysubscribe to updates of certain information from the MME/SGSN e.g. RadioAccess Technology (RAT), location information etc. for a certainMME/SGSN-PCRF session. When the subscribed information change for theconcerned PDN connection or PDP context, the MME/SGSN may initiate a newmessage for the associated MME/SGSN-PCRF-session to inform the PCRF ofthe updated information. The PCRF may also provision updated policydecisions for a PDN connection or a PDP context to the MME/SGSN in anunsolicited manner over the associated MME/SGSN-PCRF session at any timee.g. depending on internal or external events that may affect thepolicies.

The functionality of the MME/SGSN-PCRF interface may include e.g.:

-   -   Reporting of user location information to the PCRF over the        MME/SGSN-PCRF interface.    -   Provisioning of Subscriber Profile ID/RAT/Frequency Selection        Priority (SPID/RFSP) index from the PCRF to the MME/SGSN over        the MME/SGSN-PCRF interface.    -   PDN-GW selection from the PCRF to the MME/SGSN over the        MME/SGSN-PCRF interface.    -   Access Point Name (APN) selection from the PCRF to the MME/SGSN        over the MME/SGSN-PCRF interface.    -   UE-Aggregate Maximum Bit Rate (UE-AMBR) provisioning from the        PCRF to the MME/SGSN over the MME/SGSN-PCRF interface.    -   Provisioning of Radio Access Network (RAN) inactivity timers        from the PCRF to the MME/SGSN over the MME/SGSN-PCRF interface.        RSZI

Regional Subscription Zone code Identity (RSZI) is a 3GPP Release 8(Rel-8) feature which intends to make it possible for the operator tofreely and with great flexibility either restrict or allow a singlespecific subscriber in any preconfigured Geographical Area (GA) of thesubscriber's current PLMN. Each geographical area corresponds to a socalled Zone Code. FIG. 2 illustrates an overview of the RSZI.

The feature has as a prerequisite that the PLMN is divided intogeographical areas. For E-UTRAN access, each geographical area mayconsist of one or several Tracking Areas (TAs), and for UTRAN and GERANaccess, the geographical area may consist of one or more Routing Areas(RA). The maximum number of TAs is the number of TAs that the PLMN iscovering, and the maximum number of RAs is the number of RAs that thePLMN is covering.

There are two local configurations needed in the system. Firstly theHome Subscriber Server (HSS) 201 which holds the maximum number of 10Zone Codes for each subscriber and the current PLMN (indicated with ZC1. . . ZC10 in FIG. 2). This list of the zone codes is a part ofsubscription data per UE that the HSS 201 sends to the MME 203 duringdifferent mobility procedures such as Attach, TAU and handover when anUpdate Location procedure takes place. Note that an Update Locationprocedure does not take place e.g. during periodic TAU or during certainintra-MME TAU scenarios when the UE remains in a TA within the sameTA-list. The HSS 201 has the possibility to either delete the existingZone Codes or to modify them. The HSS 201 does not hold any accessinformation.

Secondly, the MME 203 needs to be configured with the access informationand corresponding Zone Codes which may differ from the Zone Codes heldby the HSS 201. If they differ then it means that the RSZI is not activeand other restriction and access policies rule.

At the MME 203, a ZC_profile is created and associated to anInternational Mobile Subscriber Identity Number Series (IMSINS) and thena list is created and associated to the profile to contain the ZoneCodes. This list is per PLMN and user specific and is tagged with arule: Either allow or restrict. The Zone Codes are created andassociated to the lists. Then the defined geographical areas withrespect to which TAs they cover are associated to the Zone Codes. As anexample, FIG. 2 illustrates a ZC_List for UE1 with allowed zones, aZC_List for UE2 with restricted zones and a ZC_List for UE3 with allowedzones.

When the configuration is done and the subscriber is associated with oneor several Zone Codes then the access information is managed.

For E-UTRAN access, at the end of each mobility procedure, the MME 203sends an updated Handover Restriction List (HRL) towards the RAN node,e.g. an evolved NodeB (eNB) 205, and an updated Non Access Stratum (NAS)Equivalent PLMN List towards the UE 208. For UTRAN access (i.e. 3G), theSGSN may perform a similar procedure. In UTRAN, the Shared NetworkAccess (SNA) codes may be seen as being similar to the HRL. The SNAcodes are sent from the SGSN to the RAN node. Based on the SNA codes,the restrictions may be decided.

The HRL contains the information that the eNB 205 needs when a Handoverprocedure is about to be initiated. The HLR is exemplified in FIG. 2 asTA1 . . . TAmax. The forbidden TAs may be for example maximum 65536. TheNAS Equivalent PLMN List contains the information that the UE 208 needsto know which PLMNs are allowed for the subscriber. In FIG. 2, the NASEquivalent PLMN List is exemplified to be PLMN1 . . . PLMN16. Theupdating of these two lists is based on the comparison of the ZCsreceived from the HSS 201 and the ones configured at the MME 203. Thelist will be filtered if there are any matches based on the rule.

An exemplary use case for the RSZI is PLMN access for national roamersin a certain area such as a city (e.g. Las Vegas). Another use case forthe RSZI may be when an operator would like to have a restrictive accesspolicy for densely populated traffic areas during busy hours.Restrictive access policies could also be relevant to apply e.g. closeto sensitive buildings or sensitive areas where for security reasons(e.g. in a close proximity to the Pentagon or the Kreml).

From an operator's point of view, the RSZI is a complicated feature toconfigure and maintain.

For the MME/SGSN configuration, the number of GAs and ZCs could easilybecome unmanageable for the MME/SGSN. This may be a problem for examplewhere e.g. the number of applicable zone codes may be more than 100.

Each list, containing ZCs, associated with a UE and the current PLMNmust have only one kind of permission, either allow or restrict. Thismeans that the UE may explicitly be either allowed or restricted andimplicitly the opposite in the remaining areas of the current PLMN. Thisis complicated enough. But when the RSZI collides with the RoamingRestriction (RR) it will be more complicated. When the RSZI indicatesexplicitly allowed, then the RR is overridden. But when the RSZIindicates implicitly allowed, then the RSZI shall be overridden by theRR. To summarize, a very complicated logic is needed especially whentaking roaming restriction aspects into account.

The RSZI requires a very static and inflexible configuration of the HSS.The operator configures the HSS with maximum of 10 ZCs per user and itscurrent PLMN. If new ZCs are needed then re-configuration must takeplace.

With the limitation on maximum number of ZCs in the HSS and the absenceof an automatic synchronization of the configuration in the MME/SGSN andthe HSS, there is a huge risk for configuration mismatch. Note that itvery likely that a configuration mismatch may be undetected by agoverning network management system as long as the configurations in theSGSN/MME and the HSS are still syntactically correct.

The possible and perhaps needed huge number of ZCs and GAs will lead tounnecessary problems at maintenance and trouble shooting.

The standard/existing functionality for the RSZI may also be consideredto be rather inflexible and static. Zone Codes are provided duringAttach/PDP-Context activation and in addition at an Update LocationRequest, i.e. at MME/SGSN change when the UE moves out of range from thecurrent TA-list. This implies that a UE may actually move within arather large geographical area (i.e. within all TAs in the same TA-list)without the Update Location Request being issued towards the HSS. Thus,even if the HSS would implement some form of smart logic that adapts theprovided ZCs to the MME/SGSN for a certain UE based on location, thisinformation could not be updated very often.

SUMMARY

An objective of embodiments herein is therefore to obviate at least oneof the above disadvantages and to provide improved handling of a UEsaccess to a mobile communications network.

According to a first aspect, the object is achieved by a method in apolicy node for handling a UEs access to a mobile communicationsnetwork. The policy node comprises policy information for the UEs accessrights to the network. The policy node obtains, from a subscriberdatabase, subscription information for a subscriber associated with theUE. Based on the subscription information and the policy information,the policy node determines which geographical areas comprised in themobile communications network the UE is allowed or denied access to. Thepolicy node transmits, to a mobility node, access information indicatingwhich geographical areas comprised in the mobile communications networkthe UE is allowed or denied access to.

According to a second aspect, the object is achieved by a method in amobility node for handling a UEs access to a mobile communicationsnetwork. The mobility node receives, from a policy node, accessinformation indicating which geographical areas comprised in the mobilecommunications network the UE is allowed or denied access to. The accessinformation is based on subscription information for a subscriberassociated with the UE and policy information for the UEs access rightsto the mobile communications network. The mobility node creates handoverrestriction information based on the received access information fromthe policy node. The mobility node transmits the handover restrictioninformation to a RAN node.

According to a third aspect, the object is achieved by a policy node forhandling a UEs access to a mobile communications network. The policynode comprises policy information for the UEs access rights to themobile communications network. The policy node is arranged to obtain,from a subscriber database, subscription information for a subscriberassociated with the UE. The policy node is arranged to, based on thesubscription information and the policy information, determine whichgeographical areas comprised in the mobile communications network the UEis allowed or denied access to. The policy node is arranged to transmit,to a mobility node, access information indicating which geographicalareas comprised in the mobile communications network the UE is allowedor denied access to.

According to a fourth aspect, the object is achieved by a mobility nodefor handling a UEs access to a mobile communications network. Themobility node is arranged to receive, from a policy node, accessinformation indicating which geographical areas comprised in the mobilecommunications network the UE is allowed or denied access to. The accessinformation is based on subscription information for a subscriberassociated with the UE and policy information for the UEs access rightsto the mobile communications network. The mobility node is arranged tocreate handover restriction information based on the received accessinformation from the policy node. The mobility node is arranged totransmit the handover restriction information to a RAN node.

Since the access to the geographical areas in the mobile communicationsnetwork is based on both the subscription information and the policyinformation, the handling of the UEs access to the mobile communicationsnetwork is improved.

Embodiments herein afford many advantages, of which a non-exhaustivelist of examples follows:

By allowing for the policy node to dynamically set accessrestriction—both geographically and per access (e.g. 3G and 4G) theembodiments herein provide an advantage of regional subscriptions with ausage limit (volume or time). For example, 4G access in inner Londonlimited to 100 MB per day for bronze level subscriptions. After 100 MBonly Second Generation (2G) and Third Generation (3G) access is allowedfor the user until the next day. Another advantage may be an emergencylockout of arbitrary geographical area for 3G and/or Fourth Generation(4G) for a PLMN. In a disaster situation, 4G access for a certain PLMNin the affected area is allowed (only) for public safety users (normallyit may be so that they do not have access to this PLMN). When thishappens all normal users may be restricted to 2G and 3G access in thesame area if needed. This requires public safety authorities tointegrate with the policy node.

A further advantage is that the embodiments herein yield optimizationfor low Average Revenue Per User (ARPU) countries. For example, 3Gand/or 4G access in high density areas are usage limited. However, whena user reach his/hers limit an Short Message Service (SMS) is sent withinformation on less dense/congested areas where 3G/4G usage is notlimited.

In addition to the advantages mentioned above, there are also advantagesrelated to OPerational EXpenditure (OPEX) savings and increasedflexibility for an operator with the embodiments herein. Since thecontrol has been centralized to the policy node, there is no longer aneed to configure or re-configure the mobility with GA access rights perUE International Mobile Subscriber Identity (IMSI) series. Anotheradvantage is that there is no longer a need to configure the mobilitynode and the subscriber database with ZCs. With a single point ofcontrol the risk for misalignment between the subscriber database andthe mobility node, configurations are efficiently eliminated.

Another advantage of the embodiments herein is that there is no need tomap ZC to the MME/SGSN local configuration (processing saving). With theembodiments herein, access restrictions may be changed by the policynode at any time on the fly. This is impossible with the standard RSZIfunctionality since access restrictions needs to be configured in themobility node but is updated only in the subscriber server.

The embodiments herein are superior compared to the current technologyboth in terms of flexibility and with regard to OPEX.

The embodiments herein are not limited to the features and advantagesmentioned above. A person skilled in the art will recognize additionalfeatures and advantages upon reading the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments herein will now be further described in more detail inthe following detailed description by reference to the appended drawingsillustrating the embodiments and in which:

FIG. 1 is a schematic block diagram illustrating embodiments of a PCCarchitecture.

FIG. 2 is a schematic block diagram illustrating RSZI.

FIG. 3 is a schematic block diagram illustrating embodiments of acommunications system.

FIG. 4 is a schematic block diagram illustrating embodiments of acommunications system.

FIG. 5 is a signaling diagram illustrating embodiments of a method.

FIG. 6 is a signaling diagram illustrating embodiments of an attach orprimary PDP-context activation procedure.

FIG. 7 is a signaling diagram illustrating embodiments of a TAUprocedure without SGW change.

FIG. 8 is a signaling diagram illustrating embodiments of PCRF initiatedchanges to regional subscription data.

FIG. 9 is a flow chart illustrating embodiments of a method performed bya policy node.

FIG. 10 is a schematic block diagram illustrating embodiments of apolicy node.

FIG. 11 is a flow chart illustrating embodiments of a method performedby a mobility node.

FIG. 12 is a schematic block diagram illustrating embodiments of amobility node.

The drawings are not necessarily to scale and the dimensions of certainfeatures may have been exaggerated for the sake of clarity. Emphasis isinstead placed upon illustrating the principle of the embodimentsherein.

DETAILED DESCRIPTION

The RSZI is a 3GPP Rel-8-feature which intends to make it possible forthe operator to either restrict or allow a single specific subscriber inany preconfigured geographical area of the subscriber's current PLMN.This feature requires complicated configuration in the HSS and in theMME/SGSN. The feature is also rather demanding from a processing pointof view for the MME/SGSN. The standardized version of RSZI offers nosupport for dynamic changes of access restrictions based on e.g. datausage.

The current technology is rather blunt/one-dimensional considering thatdynamic conditions cannot be taken into account i.e. traffic density,time of the day, data usage etc. This implies that an operator cannotcreate value packs/subscriptions that take such dynamic conditions intoconsiderations.

The embodiments herein therefore allow for the mobility node to requestaccess information from the policy node over a direct interface and toallow the policy node to provide this information to the mobility nodebased on subscription and IP-CAN session specific information such aslocation, accumulated data usage, terminal type etc.

FIG. 3 depicts a communications system 300 in which embodiments hereinmay be implemented. The communications network 300 may in someembodiments apply to one or more radio access technologies such as forexample 2G, 3G, 4G, Fifth Generation (5G) or any other 3GPP radio accesstechnology, or other radio access technologies such as Wireless LocalArea Network (WLAN). The communications system 300 may also be referredto as e.g. a wireless communications network, a wireless communicationssystem, a communications network, a network or a system.

The communications system 300 comprises a UE 301 served by a RAN node303 and is in this case capable of communicating with the RAN node 303over a communications link.

The UE 301 may be a device by which a subscriber may access servicesoffered by an operator's network and services outside operator's networkto which the operator's radio access network and core network provideaccess, e.g. access to the Internet. The UE 301 may be any device,mobile or stationary, enabled to communicate in the communicationsnetwork, for instance but not limited to e.g. user equipment, mobilephone, smart phone, sensors, meters, vehicles, household appliances,medical appliances, media players, cameras, Machine to Machine (M2M)device, Device to Device (D2D) device, Internet of Things (IoT) deviceor any type of consumer electronic, for instance but not limited totelevision, radio, lighting arrangements, tablet computer, laptop orPersonal Computer (PC). The UE 301 may be portable, pocket storable,hand held, computer comprised, or vehicle mounted devices, enabled tocommunicate voice and/or data, via the radio access network, withanother entity, such as another UE or a server.

The RAN node 303 may be a base station such as a NodeB, an eNodeB, RadioNetwork Controller (RNC), or any other network unit capable tocommunicate over a radio carrier with the UE 301.

As seen in FIG. 3, the communications system 300 further comprises amobility node 305, a policy node 308 and a subscriber database 310.

The mobility node 305 is a node which is arranged to control and handlethe mobility of the UE 301. This may also be described as providingpacket-data switching and mobility/session management. The mobility node305 may be an MME (e.g. in a 4G system), a SGSN (e.g. in a 2G or 3Gsystem) or a combined MME and SGSN node. The combined node may bereferred to as MME/SGSN. The SGSN may be referred to as a S4-SGSN. Themobility node 305 may be arranged to communicate with the RAN node 303and the policy node 308, and possibly also with other nodes in thecommunications system 300.

The policy node 308 is a node which is arranged to handle policies andcharging associated with the UE 301. The policy node 308 may be forexample a PCRF. The policy node 308 may be arranged to communicate withthe mobility node 305 and the subscriber database 310.

The subscriber database 310 is a database which is arranged to comprisesubscriber information per PDN. Such subscriber information may be forexample information about a subscriber's allowed services, Informationabout a subscriber's allowed QoS (e.g. Maximum Bit Rate (MBR) andGuaranteed Bit Rate (GBR)), a subscriber's charging related information,subscriber category information etc. The subscriber information may alsobe referred to as subscription information. The subscriber database 310may be a SPR or a front-end to a HSS.

In some embodiments, the RAN node 303 may be seen as being located in aradio access network, and the mobility node 305, the policy node 308 andthe subscriber database 310 may be seen as being located in a corenetwork.

It should be noted that the communication links between the nodes in thecommunications system 300 may be of any suitable kind including either awired or wireless link. The links may use any suitable protocoldepending on type and level of layer (e.g. as indicated by the OpenSystems Interconnection model (OSI) model).

The communications system 300 may comprise additional nodes which arenot illustrated in FIG. 3. An example of some of these nodes will beillustrated in and described with reference to FIG. 4 below.

FIG. 4 depicts a detailed exemplary architecture model of thecommunications system 300 in FIG. 3. The example illustrated in FIG. 4applies the radio access technology referred to as E-UTRAN or Long TermEvolution (LTE).

The communications system 300 illustrated in FIG. 4 comprises a UE 301which is served by a RAN node 303 (not illustrated in FIG. 4). The RANnode 303 is comprised in the E-UTRAN 403. As mentioned earlier, the RANnode 303 may be for example an eNB or any other element capable tocommunicate with the UE 303. The reference point between the UE 301 andthe E-UTRAN 403 may be referred to as LTE-Uu.

A MME 405 may be connected to the E-UTRAN 403 via the reference pointS1-MME. The MME 405 may be described as an element or node havingfunctions such as e.g. NAS signaling, Inter Core Network node signalingfor mobility between 3GPP access networks, UE reachability, TA listmanagement, PDN-GW and SGW selection, MME selection for handover withMME change etc. S10 is the reference point between MMEs 405 for MMErelocation and MME to MME information transfer. The MME 405 is anexample of the mobility node 305 in FIG. 3.

The communications system 300 may comprise two gateways, i.e. the SGW415 and the PDN-GW 418. The SGW 415 and the PGW 418 may be implementedin one physical node or in separate physical nodes. The SGW 415 is thegateway which terminates the interface towards E-UTRAN 403. Thereference point between the SGW 415 and the E-UTRAN 403 for the perbearer user plane tunneling and inter eNodeB path switching duringhandover may be referred to as S1-U. The SGW 415 routes and forwardsuser data packets, while also acting as the mobility anchor for the userplane during inter-eNodeB handovers and as the anchor for mobilitybetween LTE and other 3GPP technologies (relaying the traffic between2G/3G systems and the PDN-GW 418) etc. S11 is the reference pointbetween the SGW 415 and the MME 405.

The PDN-GW 418 may be described as the gateway which terminates the SGiinterface towards the PDN. The PDN is illustrated in FIG. 4 by theOperator's IP Services (e.g. IMS, PSS etc.) 420. PSS is short for PacketSwitched Streaming. If the UE 301 is accessing multiple PDNs, there maybe more than one PDN-GW 418 for that UE 301. Functions of the PDN-GW 418are e.g. providing connectivity from the UE 301 to external PDNs bybeing the point of exit and entry of traffic for the UE 301, performingpolicy enforcement, packet filtering for each user, charging support,lawful interception and packet screening etc. S5 is the reference pointwhich provides user plane tunneling and tunnel management between theSGW 418 and the PDN-GW 418.

The SGSN 413 is a node which is responsible for the delivery of datapackets from and to the UE's 301 within its geographical service area.One of the SGSN's 413 functions is to provide signaling for mobilitybetween 2G/3G and E-UTRAN 403 3GPP access networks. 2G/3G access networkare exemplified with GERAN 423 and UTRAN 425 in FIG. 4. Some furtherfunctions of the SGSN 413 are to handle packet routing and transfer,mobility management (attach/detach and location management), logicallink management, and authentication and charging functions etc. S3 isthe interface between the SGSN 413 and the MME 405. S4 is a referencepoint between the SGSN 413 and the SGW 415. S12 is the reference pointbetween the SGW 415 and the UTRAN 425.

The HSS 410 is a subscriber server node similar to the GSM Home LocationRegister (HLR) and Authentication Centre (AuC). The HSS 410 comprisessubscription-related information (subscriber profiles), performsauthentication and authorization of the user, and may provideinformation about the subscriber's location and IP information. Thereference point S6a enables transfer of subscription and authenticationdata for authenticating/authorizing user access to the evolved system(AAA interface) between the MME 405 and the HSS 410.

The PCRF 408 is a policy and charging control element. The PCRF 408encompasses policy control decision and flow based charging controlfunctionalities, it provides network control regarding the service dataflow detection, gating, QoS and flow based charging etc. The PCRF 408may be described as a functional entity which may be a standalone nodeor a function implemented in another node. The PCRF 408 may be anexample of the policy node 308 illustrated in FIG. 3.

The reference point Gx provides transfer of (QoS) policy and chargingrules from the PCRF 408 to a PCEF in the PDN-GW 418.

Rx is the reference point which resides between the PCRF 408 and theOperator's IP Services 420. The Rx reference point is used to exchangeapplication level session information between the PCRF 408 and the AF.

Similar to FIG. 3, it should be noted that the communication links inthe communications system illustrated in FIG. 4 may be of any suitablekind including either a wired or wireless link. The link may use anysuitable protocol depending on type and level of layer (e.g. asindicated by the (OSI model).

The method for handling the UEs 301 access to a mobile communicationsnetwork (e.g. a PLMN), according to some embodiments will now bedescribed with reference to the signaling diagram depicted in FIG. 5.The UEs 301 access to the mobile communications network may also bedescribed as the UEs 301 access rights to PLMNs specified per radioaccess technology. The method illustrated in FIG. 5 comprises at leastsome of following steps, which steps may as well be carried out inanother suitable order than described below.

Step 500

The mobility node 305 may send a request message to the policy node 308.The request message is a request for access information, i.e. a requestfor information which indicates which geographical areas in the mobilecommunications network the UE 301 is allowed access to or denied accessto or both allowed and denied access to. The request message maycomprises a UE 301 identity, network identity (e.g. PLMN ID),information indicating a radio access technology applied by the network,an area identity indicating a logical or geographical region within thenetwork (e.g. Routing Area Identity (RAI) or Tracking Area Identity(TAI)) etc.

Step 501

The policy node 308 obtains subscription information for a subscriberassociated with the UE 301. In some embodiments, the policy node 308 maysend a request for the subscription information to the subscriberdatabase 310 and receive the subscription information as a response tothe request message. In other embodiments, the policy node 308 mayreceive the subscription information from the subscriber database 310without sending any request, e.g. it may receive the information on aregular basis or when the information has been updated. The subscriptioninformation may be organized in any suitable format such as e.g. a list,a table etc.

A subscriber may remove his/hers SIM card from the UE 301 and useanother UE 301 to access the mobile communications network. In suchscenario, the subscription information will still be the same since itis for the subscriber, and not for the UE 301.

Step 502

The policy node 308 determines which geographical areas in the mobilecommunications network the UE 301 is allowed access to or denied accessto or both allowed and denied access to. The policy node 308 may takethis decision based on the subscription information obtained in step 501and also based on policy information for the UEs 301 access rights tothe mobile communications network. The policy information for the UEs301 access rights to the mobile communications network may beinformation which the policy node 308 has previously received orinformation which is preconfigured in the policy node 308.

For example, the UE 301 associated with the subscriber which thereceived subscription information relates to, may be allowed to accessgeographical areas 1, 2 and 5 and denied access to graphical areas 3 and4.

For a regional subscription, a geographical area may be allowed forexample during a certain time of day, when a user is using a certaintype of UE 301, as long as the user has not surpassed its usage limit(e.g. Megabytes or time) for a pre-defined time given by thesubscription e.g. current month. Access may also be allowed based on acombination of subscription type (e.g. gold, silver, bronze) and networkload e.g. bronze users are allowed in an area during times of low tomedium load. Access to an area may be denied in scenarios which areopposite of the allowed scenarios. For example, bronze users may not beallowed in a geographical area when there is a high risk for congestion.Another example may be that a user may not be allowed in a geographicalarea of a PLMN when a usage limit has been surpassed e.g. access to 4Gin Las Vegas is limited to 100 MB per day.

Step 503

The policy node 308 sends access information to the mobility node 305.The access information indicates which geographical areas in the mobilecommunications network the UE 301 is allowed or denied access to, i.e.the result of the decision taken in step 502. The access information maybe per radio access technology and per PLMN identity. This step may be aresponse to the request message in step 500.

Step 504

Based on the received access information, the mobility node 305 createsat least one of handover information and equivalent network information.

The handover information indicates which geographical areas the UE 301associated with the specific subscriber is forbidden to access, it mayindicate which geographical areas the UE 301 is allowed to access orindicate both which geographical areas the UE 301 is forbidden andallowed to access. The handover information may comprise informationabout geographical and logical regions, e.g. TA, Location Area (LA) andPLMN. The handover information may be for example a HRL. The handoverinformation may be transmitted to the RAN node 303.

The equivalent network information may be for example a NAS equivalentPLMN list. The NAS equivalent PLMN list is list of PLMNs that are notthe Home PLMN of the UE 301, but that the UE 301 may treat as beingequal to its home PLMN. This is used in network sharing situations whentwo operators have an agreement to allow the other operator's customersinto their RANs for coverage or capacity reasons.

Step 505

The mobility node 305 transmits the handover information to the RAN node303. With the handover information, the RAN node 303 may steer a UE 301in connected state into selecting a target PLMN and Geographical Area,e.g. TA for E-UTRAN and RA for GERAN and UTRAN accesses, during handoverprocedures.

The handover information (e.g. a HRL) may send over the S1-MME interfaceto the RAN node 303. The handover information may be sent in messagesuch as e.g.:

-   -   Downlink NAS transport message (This message is sent by the        mobility node 305 and is used for carrying NAS information over        the S1 interface).    -   Handover Request message (This message is sent by the mobility        node 305 to the target RAN node 303 to request the preparation        of resources).    -   Initial context setup request (This message is sent by the        mobility node 305 to request the setup of a UE context).        Step 506

The mobility node 305 may send the equivalent network information to theUE 301. With the equivalent network information, the UE 301 in idlestate may be steered into selecting a target PLMN during procedures suchas attach, Tracking Area Update (applicable to E-UTRAN), and RoutingArea Update (applicable to UTRAN and GERAN). The handover informationand the equivalent network information are created by mobility node 305and stored at the mobility node 305.

The equivalent network information may be sent e.g. using the NASprotocol, to the UE 301. The transmission of the equivalent networkinformation may be transparent to the RAN node 303. The equivalentnetwork information may be sent in messages such as e.g.:

-   -   Tracking area update accept (This message is sent by the        network, e.g. the mobility node 305, to the UE 301 to provide        the UE 301 with EPS mobility management related data in response        to a tracking area update request message).    -   Attach accept (This message is sent by the network, e.g. the        mobility node 305, to the UE 301 to indicate that the        corresponding attach request has been accepted).

In some embodiments, the mobility node 305 does not create theequivalent network information. In such embodiment, the mobility node305 sends the access information further to the UE 301, and the UE 301is the one which creates the equivalent network information based on thereceived access information.

Some embodiments of the method for handling a UEs 301 access to a mobilecommunications network will now be described with reference to FIGS. 6,7 and 8 using E-UTRAN access as an example. Note that E-UTRAN is onlyused as an example, and that the embodiments herein are equallyapplicable for e.g. UTRAN and GERAN accesses. FIG. 6 illustrates anattach/primary PDP-context activation procedure, FIG. 7 illustrates aTAU without a SGW change and FIG. 8 illustrates a PCRF initiated changeto regional subscription data.

Attach/Primary PDP-Context Activation

FIG. 6 is a signaling diagram illustrating an example embodiment of themethod for handling a UE 301 access to a mobile communications networkin an Attach/Primary PDP-context activation procedure. The methodillustrated in FIG. 6 comprises at least some of the following steps,which steps may be performed in any suitable order than described below:

Step 601

An attach procedure or a UE requested PDN-connectivity procedure takesplace. The attach procedure may be performed because the UE 301 needs toregister with the network to receive services that require registration.The UE requested PDN-connectivity procedure is a procedure initiated bythe UE 301 to request PDN connectivity for the UE 301.

Step 602

The MME 405 sends an Update Location Request message to the HSS 410. Therequest message indicates the MME's 405 support for regional accessrestrictions functionality.

Step 603

The HSS 410 acknowledges the Update Location request message in step 602by sending an Update Location Acknowledgement (Ack) message back to theMME 405. With the current technology, if due to regional subscriptionrestrictions the UE 301 is not allowed to attach in the TA, the MME 405rejects the Attach Request/PDN-Connectivity procedure with anappropriate cause. However with the embodiments herein this decision isdeferred until step 605 below.

Step 604

This step corresponds to step 500 in FIG. 5. The MME 405 sends a requestmessage to the PCRF 408 over a direct interface. The request message isa request for access information and comprises information whichindicates that the MME 405 has support for regional access restrictions.The MME 405 also includes at least one of the PLMN-ID, RAT, TAI/RAI,MSISDN, IMSI, International Mobile Equipment Identity (IMEI) and APN inthe request message.

Step 605

This step corresponds to step 502 and step 503 in FIG. 5. Based onpolicies and considering subscription information retrieved from thesubscriber database 310 (e.g. the SPR), the PCRF 408 decides whichgeographical areas that the UE 301 is allowed and not allowed to accessand provides this information in a response message sent back to the MME405. This information may be handover information (e.g. organized in theform of a list such as a HRL) indicating allowed and not allowed TA, RAper access technology (e.g. 2G/3G/4G) and PLMN-ID. The PCRF 408 may alsorequest from the MME 405 to be informed about TA/RA changes for this UE301. If due to regional subscription restrictions the UE 301 is notallowed to attach in the TA, the MME 405 rejects the AttachRequest/PDN-Connectivity procedure from step 601 with an appropriatecause for the rejection. If the Attach Request/PDN-Connectivityprocedure in step 601 was rejected due to regional subscription, roamingrestrictions or access restrictions, the MME 405 may terminate theassociated session towards the PCRF 408 (e.g. the direct interfacebetween the MME 405 and the PCRF 408).

Step 606

The MME 405 sends a Create Session Request message to the SGW 415.

Step 607

The SGW 415 sends the Create Session Request to the PDN-GW 418.

Step 608

The PDN-GW 418 initiates a new Gx session with the PCRF 408 by sendingan initiate Gx session request message to the PCRF 408.

Step 609

The PCRF 408 responds to the Gx session request in step 608 by sendingan initiate Gx session response message back to the PDN-GW 418.

Step 610

The PDN-GW 418 sends a Create Session Response message to the SGW 415.The response message is a response to the request message in step 607.

Step 611

The SGW 415 sends the Create Session Response message to the MME 405.The response message is a response to the request message in step 606.

Step 612

This step corresponds to step 504, step 505 and step 506 in FIG. 5. TheMME 405 constructs the handover information (e.g. a HRL), based on theaccess restrictions received from the PCRF 408 in step 605. Furthermore,the MME 405 may also construct the equivalent network information (e.g.the NAS equivalent PLMN list). Note that the information provided by thePCRF 408 may supersede any potential access restrictions received fromHSS 410 or MME local configuration. The MME 405 sends one of an InitialContext Setup Request message, an Attach Accept message or aPDN-Connectivity Accept message The Initial Context Setup Requestmessage may comprise the HLR and is sent to the eNodeB 403. The AttachAccept message may comprise the equivalent network information and issent to the UE 301.

Step 613

In case of an attach procedure or an UE requested PDN-connectivityprocedure was initiated in step 601, this procedure now continues.

TAU without SGW Change

FIG. 7 is a signaling diagram illustrating an example embodiment of themethod for handling a UEs 301 access to a mobile communications networkin a TAU procedure without SGW 415 change. The method illustrated inFIG. 7 comprises at least some of the following steps, which steps maybe performed in any suitable order than described below:

Step 701

An E-UTRAN TAU procedure without SGW 415 change takes place. A trackingarea update procedure is initiated by the UE 301 and occurs when aGPRS-attached or E UTRAN-attached UE 301 enters a new tracking area,when a tracking area timer has expired etc. This may involve that the UE301 sends a TAU request message to the eNodeB 403.

Step 702

The eNodeB 403 forwards the TAU Request message to the new MME 405.

Step 703

In case the new MME 405 detects that there has been an MME/SGSN 405change, the new MME 405 sends a Context Request message to the oldMME/SGSN 405 to retrieve the user information. If the new MME 405 doesnot detect that there has been any MME/SGSN change, step 703, 704 and705 are skipped. This is indicated with dotted arrows in FIG. 7.

Step 704

If the Context Request message is sent to an old MME/SGSN 405 in step703, the old MME/SGSN 405 responds by sending a Context Response messageto the MME 405.

Step 705

The new MME 405 sends a Context Acknowledge message to the old MME/SGSN405. In case the old MME/SGSN 405 has an ongoing session towards thePCRF 408, then this session is now terminated by the old MME/SGSN 405(not illustrated in FIG. 7).

Step 706

This step corresponds to step 500 in FIG. 5. If the TA has changed andthe PCRF 408 has requested to be updated on TA changes (as described inrelation to FIG. 6, step 605) then the MME 405 sends a request messageto the PCRF 408 and includes the new TAI. If there has been a MME/SGSN405 change, the new MME 405 sends a request to the PCRF 408 over adirect interface and indicates that the MME 405 supports regional accessrestrictions. The MME 405 also includes at least one of the PLMN-id,RAT, TAI/RAI, MSISDN, IMSI, IMEI and APN in the request message.

Step 707

This step corresponds to step 502 and step 503 in FIG. 5. Based onpolicies and considering subscription information retrieved from theSPR, the PCRF 408 decides which geographical areas that are allowed/notallowed for the UE 301 to access and provides this information in aresponse back to the MME 405. This information contains e.g. a list ofnot allowed TA, RA per access technology (e.g. 2G/3G/4G) and PLMN-id. Ifthe request message in step 706 was from a new MME 405, the PCRF 408also requests from the MME 405 to be informed about TA changes for thisUE 301. If due to regional subscription restrictions the UE 301 is notallowed to attach in the TA, the MME 405 rejects the TAU procedure withan appropriate cause for the rejection. If the TAU request was rejecteddue to regional subscription, roaming restrictions or accessrestrictions the MME 405 may terminate the associated session towardsthe PCRF 408.

Step 708

The E-UTRAN TAU procedure continues in step 708.

Step 709

This step corresponds to step 504, step 505 and step 506 in FIG. 5. TheMME 405 constructs the equivalent network information, e.g. in the formof a NAS equivalent PLMN list. Note that the information provided by thePCRF 408 may supersede any potential access restrictions received fromHSS 410 or MME local configuration. The MME 405 sends a Tracking AreaUpdate Accept message to the UE 301. The equivalent network informationis included to the UE 301 if required. The TAU Accept message may besent via the eNodeB 403 to the UE 301.

Step 710

If the UE 301 detects from the TAU accept message in step 709 that aGlobally Unique Temporary UE Identity (GUTI) has been changed, the UE301 may acknowledge the new GUTI by returning a Tracking Area UpdateComplete message to the MME 405. If there has not been any GUTI change,this step 710 is not performed, indicated with a dotted arrow in FIG. 7.

As mentioned above, FIG. 7 illustrates a TAU procedure without SGWchange. However, the same principles also apply for a RAU procedure anda TAU procedure with SGW change.

Handover Procedures

For a S1 handover, the Handover Restriction List may be provided by thetarget MME 405 already when Handover Request is sent to the TargeteNodeB 403. Prior to this step it may be possible for the target MME 405to interact with the PCRF 408 over the direct interface in order toretrieve updated information regarding allowed/not allowed TA/RA.However, this information may take too long time to obtain due to theextra signaling and processing in the PCRF 408 and the MME 405. Sincehandover procedures are very time critical, they may not be recommended.However, since the initiated handover is already checked against theHandover Restriction List in the Source eNodeB 403 it is clearly validand the provisioning of the new handover information (e.g. a HLR) fromthe Target MME 405 to the Target eNodeB 403 is only related to the nextpotential handover. The standard S1 handover procedure already includesa TAU procedure and it is in this step that the new handover informationand the equivalent network information are created based on input fromthe PCRF 408.

In addition, for the X2 handover, the procedure is finalized by a TAUprocedure. Since a TAU procedure has already been described above, itwill not be described here for S1 and X2 handover for the sake ofsimplicity. Also, mobility procedures for UTRAN and GERAN accessesfollows the same principles as described above.

PCRF Initiated Changes to Regional Subscription Data

An exemplary embodiment for handling when internal or externalcircumstances triggers the PCRF 408 to provision updates to theinformation regarding regional subscriptions towards the MME 405 willnow be described. FIG. 8 is a signaling diagram illustrating an exampleembodiment of the method for handling a UEs 301 access to a mobilecommunications network in a PCRF 408 initiated procedure with changes inregional subscription data. The method illustrated in FIG. 8 comprisesat least some of the following steps, which steps may be performed inany suitable order than described below:

Step 801

The PCRF 408 takes a decision that the policies for regionalsubscriptions for a specific PDN-connection/PDP-context has changed.This may for example be the case due to an internal event (time ofday/day of week change) or due to information received over externalinterfaces (data usage reporting over the Gx or the Sd interface,subscription change etc.).

Step 802

This step corresponds to step 503 in FIG. 5. The PCRF 408 sends aNotification message over the direct interface to the MME 405 thathandles the associated PDN-connection/PDP-context. The message comprisese.g. a list of not allowed TA, RA per access technology (e.g. 2G/3G/4G)and PLMN-id.

Step 803

The MME 405 acknowledges the message from the PCRF 408 in step 802 bysending a response message to the PCRF 408. The MME 405 further on savesthe newly received information for the PDN-connection. Note that if theUE 301 is in EPS Connection Management (ECM) connected mode it may notbe possible to immediately update the handover information towards theeNodeB 303, but the MME 405 may have to wait until the next applicableprocedure.

Step 804

This step corresponds to step 504 in FIG. 5. At the next Service requestmessage, TAU/RAU or handover, the MME 405 constructs the HandoverRestriction List, based on the access restrictions received from thePCRF 408 in step 803. Note that the information provided by the PCRF 408may supersede any potential access restrictions received from the HSS410 or MME local configuration. The procedure may either be rejectedwith an appropriate cause i.e. due to that the UE 301 is located in anarea that is not allowed, or accepted in which case the handoverinformation is provided to the eNodeB 303. Step 804 may be performeddirectly after step 801-803 or some time after steps 801-803, indicatedwith the dotted line in FIG. 8.

The method described above will now be described seen from theperspective of the policy node 308. FIG. 9 is a flowchart describing thepresent method in the policy node 308 for handling a UEs 301 access to amobile communications network. The policy node 308 comprises policyinformation for the UEs 301 access rights to the mobile communicationsnetwork. The policy node 308 may be a PCRF node.

The method illustrated in FIG. 9 comprises at least some of thefollowing steps to be performed by the policy node 308:

Step 900

This step corresponds to step 500 in FIG. 5, step 604 in FIG. 6 and step706 in FIG. 7. In some embodiments, the policy node 308 receives arequest message from the mobility node 305. The request message is arequest for the access information. The request message may comprise atleast one of a UE 301 identity, network identity, information indicatinga radio access technology applied by the network and an area identityindicating a logical or geographical region within the network.

The mobility node 305 may be a MME, or a SGSN or a combined MME and SGSNnode.

Step 901

This step corresponds to step 604 in FIG. 6 and step 706 in FIG. 7. Insome embodiments, the policy node 308 receives, from the mobility node305, a support indication which indicates that the mobility node 305supports reception and handling of access information indicating whichgeographical areas comprised in the mobile communications network the UE301 is allowed or denied access to.

Step 902

This step corresponds to step 501 in FIG. 5. The policy node 308obtains, from a subscriber database 310, subscription information for asubscriber associated with the UE 301. The subscriber database 310 maybe a SPR.

Step 903

This step corresponds to step 801 in FIG. 8. In some embodiments, thepolicy node 308 determines that at least one of the policy informationand the subscription information has changed. The change may be e.g.compared to previously obtained information.

Step 904

This step corresponds to step 502 in FIG. 5, step 707 in FIG. 7 and step801 in FIG. 8. Based on the subscription information and the policyinformation, the policy node 308 determines which geographical areascomprised in the mobile communications network the UE 301 is allowed ordenied access to.

The policy information and subscription information used in the decisionof which geographical areas comprised in the mobile communicationsnetwork the UE 301 is allowed or denied access to may be at least one ofthe changed policy information and changed subscription information.

In some embodiments, the decision of which geographical areas comprisedin the mobile communications network the UE 301 is allowed or deniedaccess to is taken when the policy node 308 has determined that at leastone of the policy information and subscription information has changed(e.g. step 903).

Step 905

This step corresponds to step 503 in FIG. 5, step 605 in FIG. 6, step707 in FIG. 7 and step 802 in FIG. 8. The policy node 308 transmits, toa mobility node 305, access information indicating which geographicalareas comprised in the mobile communications network the UE 301 isallowed or denied access to. The mobile communications network may be aPLMN and the access information may be per radio access technology andper PLMN identity.

Embodiments of the policy node 308 configured to perform the methodactions handling a UEs 301 access to a mobile communications network, asdescribed above in relation to FIG. 9, is depicted in FIG. 10. Thepolicy node 308 comprises policy information for the UEs 301 accessrights to the mobile communications network. The policy node 308 may bea PCRF node,

The policy node 308 is arranged to, e.g. by means of a first obtainingmodule 1001, obtain, from a subscriber database 310, subscriptioninformation for a subscriber associated with the UE 301. The firstobtaining module 1001 may also be referred to as a first obtaining unit,a first obtaining means, a first obtaining circuit or a first means forobtaining. The first obtaining module 1001 may be a first processor 1003of the policy node 308. The subscriber database 310 may be a SPR.

The policy node 308 is arranged to, e.g. by means of a first determiningmodule 1005, determine, based on the subscription information and thepolicy information, which geographical areas comprised in the mobilecommunications network the UE 301 is allowed or denied access to. Thefirst determining module 1005 may also be referred to as a firstdetermining unit, a first determining means, a first determining circuitor a first means for determining. The first determining module 1005 maybe the first processor 1003 of the policy node 308.

The policy node 308 is arranged to, e.g. by means of a firsttransmitting module 1008, transmit, to a mobility node 305, accessinformation indicating which geographical areas comprised in the mobilecommunications network the UE 301 is allowed or denied access to. Themobile communications network may be a PLMN and the access informationmay be per radio access technology and per PLMN identity. The firsttransmitting module 1008 may also be referred to as a first transmittingunit, a first transmitting means, a first transmitting circuit, a firstmeans for transmitting or a first output unit. The first transmittingmodule 1008 may be a transmitter, a transceiver etc. The firsttransmitting module 1008 may be a wireless transmitter of the policynode 308 of a wireless or fixed communications system. The mobility node305 may be a MME or a SGSN or a combined MME and SGSN node.

In some embodiments, the policy node 308 is arranged to, e.g. by meansof a first receiving module 1010, receive a request message from themobility node 305. The request message is a request for the accessinformation. The request message may comprise at least one of a UE 301identity, network identity, information indicating a radio accesstechnology applied by the network and an area identity indicating alogical or geographical region within the network. The first receivingmodule 1010 may also be referred to as a first receiving unit, a firstreceiving means, a first receiving circuit, a first means for receivingor a first input unit. The first receiving module 1010 may be areceiver, a transceiver etc. The first receiving module 1010 may be awireless receiver of the policy node 308 of a wireless or fixedcommunications system.

In some embodiments, the policy node 308 is arranged to, e.g. by meansof the first receiving module 1010, receive, from the mobility node 305,a support indication which indicates that the mobility node 305 supportsreception and handling of access information indicating whichgeographical areas comprised in the mobile communications network the UE301 is allowed or denied access to.

The policy node 308 may be arranged to, e.g. by means of the firstdetermining module 1005, determine that at least one of the policyinformation and the subscription information has changed. The policyinformation and subscription information used in the decision of whichgeographical areas comprised in the mobile communications network the UE301 is allowed or denied access to may be at least one of the changedpolicy information and changed subscription information. The decision ofwhich geographical areas comprised in the mobile communications networkthe UE 301 is allowed or denied access to may be taken when the policynode 308 has determined that at least one of the policy information andsubscription information has changed.

The policy node 308 may further comprise a first memory 1013 comprisingone or more memory units. The first memory 1013 is arranged to be usedto store data, received data streams, power level measurements, accessinformation, subscription information, information about geographicalareas, information about allowed and denied geographical areas, policyinformation, request messages, support indication, changed policyinformation, policy information, threshold values, time periods,configurations, schedulings, and applications to perform the methodsherein when being executed in the policy node 308.

Those skilled in the art will also appreciate that the first obtainingmodule 1001, the first determining module 1005, the first transmittingmodule 1008 and the first receiving module 1010 described above mayrefer to a combination of analogue and digital circuits, and/or one ormore processors configured with software and/or firmware, e.g. stored ina memory, that when executed by the one or more processors such as thefirst processor 1003 perform as described above. One or more of theseprocessors, as well as the other digital hardware, may be included in asingle application-specific integrated circuit (ASIC), or severalprocessors and various digital hardware may be distributed among severalseparate components, whether individually packaged or assembled into asystem-on-a-chip (SoC).

A first computer program may comprise instructions which, when executedon at least one processor, cause the at least one processor (e.g. thefirst processor 1003) to carry out the method as described in FIG. 9. Afirst carrier may comprise the first computer program. The first carriermay be one of an electronic signal, optical signal, radio signal orcomputer readable storage medium.

The method described above will now be described seen from theperspective of the mobility node 305. FIG. 11 is a flowchart describingthe present method in the mobility node 305 for handling a UEs 301access to a mobile communications network. The mobility node 305 may bea MME or a SGSN or a combined MME and SGSN node. The method illustratedin FIG. 10 comprises at least some of the following steps to beperformed by the mobility node 305:

Step 1100

This step corresponds to step 604 in FIG. 6 and step 706 in FIG. 7. Insome embodiments, the mobility node 305 transmits, to the policy node308, a support indication which indicates that the mobility node 305supports reception and handling of access information indicating whichgeographical areas comprised in the mobile communications network the UE301 is allowed or denied access to. The policy node 308 may be a PCRFnode.

Step 1101

This step corresponds to step 500 in FIG. 5, step 604 in FIG. 6 and step706 in FIG. 7. In some embodiments, the mobility node 305 transmits arequest message to the policy node 308. The request message is a requestfor the access information. The request message may comprises at leastone of a UE 301 identity, network identity, information indicating aradio access technology applied by the network, and an area identityindicating a logical or geographical region within the network.

Step 1102

This step corresponds to step 503 in FIG. 5, step 605 in FIG. 6, step707 in FIG. 7 and step 802 in FIG. 8. The mobility node 305 receives,from a policy node 308, access information indicating which geographicalareas comprised in the mobile communications network the UE 301 isallowed or denied access to. The access information is based onsubscription information for a subscriber associated with the UE 301 andpolicy information for the UEs 301 access rights to the mobilecommunications network.

In some embodiments, the access information received from the policynode 308 supersedes access restriction information received from anothersubscriber database (e.g. another HSS) or local configuration associatedwith access to geographical areas in the mobility node 305.

The mobile communications network may be a PLMN and the accessinformation may be per radio access technology and per network identity.

Step 1103

This step corresponds to step 803 in FIG. 8. In some embodiments, themobility node 305 transmits an acknowledgement message to the policynode 308. The acknowledgement message acknowledges the receipt of theaccess information in step 1102.

Step 1104

This step corresponds to step 504 in FIG. 5 and step 612 in FIG. 6. Themobility node 305 creates handover restriction information based on thereceived access information from the policy node 308.

Step 1105

This step corresponds to step 505 in FIG. 5, step 612 in FIG. 6 and step709 in FIG. 7. The mobility node 305 transmits the handover restrictioninformation to a RAN node 303.

Step 1106

This step corresponds to step 504 in FIG. 5, step 612 in FIG. 6 and step709 in FIG. 7. In some embodiments, the mobility node 305 createsequivalent network information.

Step 1107

This step corresponds to step 506 in FIG. 5. In some embodiments, themobility node 305 transmits the created equivalent network informationto the UE 301.

Step 1108

This step corresponds to step 605 in FIG. 6. In some embodiments, whenthe access information indicates that UE 301 is not allowed to access ageographical area in the network, the mobility node 305 determines thatthe UE's 301 request to access the geographical area in the networkshould be rejected.

Step 1109

This step corresponds to step 605 in FIG. 6. In some embodiments, themobility node 305 terminates the UE's 301 session towards policy node308. The session is associated with access to the region in the network.

An example of step 1109 may be that if the AttachRequest/PDN-Connectivity procedure was rejected due to regionalsubscription, roaming restrictions or access restrictions the mobilitynode 305 may terminate the associated session towards the policy node308 (e.g. via the Sx interface). This may be valid for e.g.Attach/PDN-connectivity. For e.g. TAU the mobility node 305 may rejectthe TAU procedure, but maintains the PDN-connection and the Sx sessiontowards the policy node 308.

Embodiments of the mobility node 305 configured to perform the methodactions handling a UEs 301 access to a mobile communications network, asdescribed above in relation to FIG. 11, is depicted in FIG. 12. Asmentioned earlier, the mobile communications network may be a PLMN andthe access information may be per radio access technology and pernetwork identity. The mobility node 305 may be a MME or a SGSN or acombined MME and SGSN node.

The mobility node 305 is arranged to, e.g. by means of a secondreceiving module 1201, receive, from a policy node 308, accessinformation indicating which geographical areas comprised in the mobilecommunications network the UE 301 is allowed or denied access to. Theaccess information is based on subscription information for a subscriberassociated with the UE 301 and policy information for the UEs 301 accessrights to the mobile communications network. The access informationreceived from the policy node 308 may supersede access restrictioninformation received from another subscriber database or localconfiguration associated with access to geographical areas in themobility node 305. The second receiving module 1201 may also be referredto as a second receiving unit, a second receiving means, a secondreceiving circuit, second means for receiving or a second input unit.The second receiving module 1201 may be a receiver, a transceiver etc.The second receiving module 1201 may be a wireless receiver of themobility node 305 of a wireless or fixed communications system. Thepolicy node 308 may be a PCRF node.

The mobility node 305 is arranged to, e.g. by means of a second creatingmodule 1203, create handover restriction information based on thereceived access information from the policy node 308. The secondcreating module 1203 may also be referred to as a second creating unit,a second creating means, a second creating circuit, means for creatingetc. The second creating module 1203 may be a second processor 1205 ofthe mobility node 305.

The mobility node 305 is arranged to, e.g. by means of a secondtransmitting module 1208, transmit the handover restriction informationto a RAN node 303. The second transmitting module 1208 may also bereferred to as a second transmitting unit, a second transmitting means,a second transmitting circuit, second means for transmitting or a secondoutput unit. The second transmitting module 1208 may be a transmitter, atransceiver etc. The second transmitting module 1208 may be a wirelessreceiver of the mobility node 305 of a wireless or fixed communicationssystem.

In some embodiments, the mobility node 305 is arranged to, e.g. by meansof the second creating module 1203, create equivalent networkinformation.

In some embodiments, the mobility node 305 is arranged to, e.g. by meansof the second transmitting module 1208, transmit the created equivalentnetwork information to the UE 301.

In some embodiments, the mobility node 305 is arranged to, e.g. by meansof the second transmitting module 1208, transmit a request message tothe policy node 308. The request message is a request for the accessinformation. The request message may comprise at least one of a UE 301identity, network identity, information indicating a radio accesstechnology applied by the network, and an area identity indicating alogical or geographical region within the network (e.g. RAI or TAI).

In some embodiments, the mobility node 305 is arranged to, e.g. by meansof the second transmitting module 1208, transmit, to the policy node308, a support indication which indicates that the mobility node 305supports reception and handling of access information indicating whichgeographical areas comprised in the mobile communications network the UE301 is allowed or denied access to.

In some embodiments, the mobility node 305 is arranged to, e.g. by meansof a second determining module 1210, when the access informationindicates that UE 301 is not allowed to access a geographical area inthe network, determine that the UE's 301 request to access thegeographical area in the network should be rejected. The seconddetermining module 1210 may also be referred to as a second determiningunit, a second determining means, a second determining circuit, secondmeans for determining etc. The second determining module 1210 may be thesecond processor 1205 of the mobility node 305.

In some embodiments, the mobility node 305 is arranged to, e.g. by meansof a second terminating module 1213, terminate the UE's 301 sessiontowards policy node 308. The session is associated with access to theregion in the network. The second terminating module 1213 may also bereferred to as a second terminating unit, a second terminating means, asecond terminating circuit, second means for terminating etc. The secondterminating module 1213 may be the second processor 1205 of the mobilitynode 305.

In some embodiments, the mobility node 305 is arranged to, e.g. by meansof the second transmitting module 1208, transmit an acknowledgementmessage to the policy node 308. The acknowledgement message acknowledgesthe receipt of the access information.

The mobility node 305 may further comprise a second memory 1215comprising one or more memory units. The second memory 1215 is arrangedto be used to store data, received data streams, power levelmeasurements, access information, subscription information, informationabout geographical areas, information about allowed and deniedgeographical areas, policy information, request messages, supportindication, changed policy information, policy information, thresholdvalues, time periods, configurations, schedulings, and applications toperform the methods herein when being executed in the mobility node 305.

Those skilled in the art will also appreciate that the second receivingmodule 1201, the second creating module 1203, the second transmittingmodule 1208, the second transmitting module 1210 and the secondterminating module 1212 described above may refer to a combination ofanalogue and digital circuits, and/or one or more processors configuredwith software and/or firmware, e.g. stored in a memory, that whenexecuted by the one or more processors such as the second processor 1205perform as described above. One or more of these processors, as well asthe other digital hardware, may be included in a single ASIC, or severalprocessors and various digital hardware may be distributed among severalseparate components, whether individually packaged or assembled into aSoC.

A second computer program may comprise instructions which, when executedon at least one processor, cause the at least one processor (e.g. thesecond processor 1205) to carry out the method as described in FIG. 11.A second carrier may comprise the second computer program. The secondcarrier may be one of an electronic signal, optical signal, radio signalor computer readable storage medium.

The present mechanism for handling a UEs 301 access to a mobilecommunications network, may be implemented through one or moreprocessors, such as a first processor 1003 in the policy nodearrangement depicted in FIG. 10 and a second processor 1205 in themobility node arrangement depicted in FIG. 12, together with computerprogram code for performing the functions of the embodiments herein. Theprocessor may be for example a Digital Signal Processor (DSP), ASICprocessor, Field-programmable gate array (FPGA) processor or microprocessor. The program code mentioned above may also be provided as acomputer program product, for instance in the form of a data carriercarrying computer program code for performing the embodiments hereinwhen being loaded into at least one of the policy node 308 and themobility node 305. One such carrier may be in the form of a CD ROM disc.It is however feasible with other data carriers such as a memory stick.The computer program code may furthermore be provided as pure programcode on a server and downloaded to at least one of the policy node 308and the mobility node 305.

Summarized, the embodiments herein allow for the mobility node 305 torequest access information (e.g. Regional Subscription information) fromthe policy node 308 over a direct interface and to allow the policy node308 to provide this information to the mobility node 305 based onsubscription and IP-CAN session specific information such as location,accumulated data usage, terminal type etc.

The mobility node 305 may request the access information from the policynode 308 during Initial Attach/PDP-Context activation and in additionduring certain mobility procedures.

If the mobility node 305 has requested the access information from thepolicy node 305, then the policy node 305 may evaluate whichgeographical areas that are allowed/not allowed and provide thisinformation back to the mobility node 305. Geographical Areas may be oneor several Tracking Areas, Routing Areas. The exact format of theinformation provided from the policy node 308 to the mobility node 305may be, but is not limited to, a list of not allowed TA/RAs per PLMN andaccess type, a range of not allowed TA/RAs per PLMN and access type.

The mobility node 305 then takes the information on not allowed areasfrom the policy node 308 into account and takes a decision to accept orreject the ongoing mobility procedure (e.g. attach, TAU/RAU, handover)towards the UE 301. If the procedure is accepted the mobility node 305builds the handover information (e.g. a HRL) taking the policy nodeprovided information into account and provides the handover informationto the RAN node 303, e.g. an eNodeB or a RNC. Furthermore, the mobilitynode 305 builds the equivalent network information and provides this tothe UE 301.

The Zone Codes from HSS 410 are ignored, if provided. Localconfiguration in the mobility node 305 may be overridden if the accessinformation is provided by the policy node 308.

During mobility procedures the not allowed areas may be updated by thepolicy node 308. The policy node 308 may also unsolicited update the notallowed areas to the mobility node 305. In this case the mobility node305 may take the updated information into account the next occasion whenthe handover information is provided to the RAN node 303 and theequivalent network information is provided to the UE 301, e.g. at thenext periodic TAU or service request.

The embodiments herein are not limited to the above describedembodiments. Various alternatives, modifications and equivalents may beused. Therefore, the above embodiments should not be taken as limitingthe scope of the embodiments, which is defined by the appending claims.

It should be emphasized that the term “comprises/comprising” when usedin this specification is taken to specify the presence of statedfeatures, integers, steps or components, but does not preclude thepresence or addition of one or more other features, integers, steps,components or groups thereof. It should also be noted that the words “a”or “an” preceding an element do not exclude the presence of a pluralityof such elements.

The term “configured to” used herein may also be referred to as“arranged to”, “adapted to”, “capable of” or “operative to”.

It should also be emphasised that the steps of the methods defined inthe appended claims may, without departing from the embodiments herein,be performed in another order than the order in which they appear in theclaims.

The invention claimed is:
 1. A method in a policy node for handling aUser Equipment's, UE's, access to a mobile communications network,wherein the policy node comprises policy information for the UE's accessrights to the mobile communications network, the method comprising:obtaining, from a subscriber database, subscription information for asubscriber associated with the UE; based on the subscription informationand the policy information, determining which geographical areascomprised in the mobile communications network the UE is allowed ordenied access to; and transmitting, to a mobility node, over a directinterface between the policy node and the mobility node, accessinformation indicating which geographical areas comprised in the mobilecommunications network the UE is allowed or denied access to, whereinthe access information is per radio access technology and per PublicLand Mobile Network, PLMN, identity.
 2. The method according to claim 1,further comprising: receiving a request message from the mobility node,wherein the request message is a request for the access information. 3.The method according to claim 2, wherein the request message comprisesat least one of a UE identity, network identity, information indicatinga radio access technology applied by the mobile communications network,and an area identity indicating a logical or geographical region withinthe mobile communications network.
 4. The method according to claim 1,further comprising: receiving, from the mobility node, a supportindication which indicates that the mobility node supports reception andhandling of the access information indicating which geographical areascomprised in the mobile communications network the UE is allowed ordenied access to.
 5. The method according to claim 1, furthercomprising: determining that at least one of the policy information andthe subscription information has changed; wherein the policy informationand the subscription information used in the decision of whichgeographical areas comprised in the mobile communications network the UEis allowed or denied access to is at least one of the changed policyinformation and the changed subscription information; and wherein thedecision of which geographical areas comprised in the mobilecommunications network the UE is allowed or denied access to is takenwhen the policy node has determined that at least one of the policyinformation and subscription information has changed.
 6. The methodaccording to claim 1, wherein the mobile communications network is aPLMN and the access information is per the radio access technology andper the PLMN identity.
 7. The method according to claim 1, wherein thepolicy node is a Policy and Charging Rules Function, PCRF, node, thesubscriber database is a Subscriber Profile Repository, SPR, and themobility node is a Mobility Management Entity, MME, or a Serving Generalpacket radio service Support Node, SGSN, or a combined MME and SGSNnode.
 8. A method in a mobility node for handling a User Equipment's,UE's, access to a mobile communications network, the method comprising:receiving, from a policy node, over a direct interface between thepolicy node and the mobility node, access information indicating whichgeographical areas comprised in the mobile communications network the UEis allowed or denied access to, wherein the access information is basedon subscription information for a subscriber associated with the UE andpolicy information for the UE's access rights to the mobilecommunications network, wherein the access information is per radioaccess technology and per Public Land Mobile Network, PLMN, identity;creating handover restriction information based on the received accessinformation from the policy node; and transmitting the handoverrestriction information to a Radio Access Network, RAN, node.
 9. Themethod according to claim 8, further comprising: creating equivalentnetwork information; and transmitting the created equivalent networkinformation to the UE.
 10. The method according to claim 8, furthercomprising: transmitting a request message to the policy node, whereinthe request message is a request for the access information.
 11. Themethod according to claim 10, wherein the request message comprises atleast one of a UE identity, network identity, information indicating aradio access technology applied by the mobile communications network,and an area identity indicating a logical or geographical region withinthe mobile communications network.
 12. The method according to claim 8,further comprising: transmitting, to the policy node, a supportindication which indicates that the mobility node supports reception andhandling of the access information indicating which geographical areascomprised in the mobile communications network the UE is allowed ordenied access to.
 13. The method according to claim 8, furthercomprising: when the access information indicates that the UE is notallowed to access a geographical area in the network, determining thatthe UE's request to access the geographical area in the mobilecommunications network should be rejected; and terminating the UE'ssession towards the policy node, wherein the session is associated withaccess to the region in the mobile communications network.
 14. Themethod according to claim 8, wherein the access information receivedfrom the policy node supersedes access restriction information receivedfrom another subscriber database or a local configuration associatedwith access to geographical areas in the mobility node.
 15. The methodaccording to claim 8, further comprising: transmitting anacknowledgement message to the policy node, wherein the acknowledgementmessage acknowledges the receipt of the access information.
 16. Themethod according to claim 8, wherein the mobile communications networkis a PLMN and wherein the access information is per the radio accesstechnology and per network identity.
 17. The method according to claim8, wherein the mobility node is a Mobility Management Entity, MME, or aServing General packet radio service Support Node, SGSN, or a combinedMME and SGSN node and wherein the policy node is a Policy and ChargingRules Function, PCRF, node.
 18. A policy node for handling a UserEquipment's, UE's, access to a mobile communications network, whereinthe policy node comprises policy information for the UE's access rightsto the mobile communications network, the policy node comprising:memory; and one or more processors associated with the memory, the oneor more processors configured to cause the policy node to: obtain from asubscriber database, subscription information for a subscriberassociated with the UE; based on the subscription information and thepolicy information, determine which geographical areas comprised in themobile communications network the UE is allowed or denied access to; andtransmit, to a mobility node, over a direct interface between the policynode and the mobility node, access information indicating whichgeographical areas comprised in the mobile communications network the UEis allowed or denied access to, wherein the access information is perradio access technology and per Public Land Mobile Network, PLMN,identity.
 19. The policy node according to claim 18, wherein the one ormore processors are further configured to: receive a request messagefrom the mobility node, wherein the request message is a request for theaccess information.
 20. The policy node according to claim 19, whereinthe request message comprises at least one of a UE identity, networkidentity, information indicating a radio access technology applied bythe mobile communications network, and an area identity indicating alogical or geographical region within the mobile communications network.21. The policy node according to claim 18, wherein the one or moreprocessors are further configured to: receive, from the mobility node, asupport indication which indicates that the mobility node supportsreception and handling of the access information indicating whichgeographical areas comprised in the mobile communications network the UEis allowed or denied access to.
 22. The policy node according to claim18, wherein the one or more processors are further configured to:determine that at least one of the policy information and thesubscription information has changed; wherein the policy information andthe subscription information used in the decision of which geographicalareas comprised in the mobile communications network the UE is allowedor denied access to is at least one of the changed policy informationand changed subscription information; and wherein the decision of whichgeographical areas comprised in the mobile communications network the UEis allowed or denied access to is taken when the policy node hasdetermined that at least one of the policy information and thesubscription information has changed.
 23. The policy node according toclaim 18, wherein the mobile communications network is a PLMN and theaccess information is per the radio access technology and per the PLMNidentity.
 24. The policy node according to claim 18, wherein the policynode is a Policy and Charging Rules Function, PCRF, node, the subscriberdatabase is a Subscriber Profile Repository, SPR, and the mobility nodeis a Mobility Management Entity, MME, or a Serving General packet radioservice Support Node, SGSN, or a combined MME and SGSN node.
 25. Amobility node for handling a User Equipment's, UE's, access to a mobilecommunications network, the mobility node comprising: memory; and one ormore processors associated with the memory, the one or more processorsconfigured to cause the mobility node to: receive, from a policy node,over a direct interface between the policy node and the mobility node,access information indicating which geographical areas comprised in themobile communications network the UE is allowed or denied access to,wherein the access information is based on subscription information fora subscriber associated with the UE and policy information for the UE'saccess rights to the mobile communications network, wherein the accessinformation is per radio access technology and per Public Land MobileNetwork, PLMN, identity; create handover restriction information basedon the received access information from the policy node; and transmitthe handover restriction information to a Radio Access Network, RAN,node.
 26. The mobility node according to claim 25, wherein the one ormore processors are further configured to: create equivalent networkinformation; and transmit the created equivalent network information tothe UE.
 27. The mobility node according to claim 25, wherein the one ormore processors are further configured to: transmit a request message tothe policy node, wherein the request message is a request for the accessinformation.
 28. The mobility node according to claim 27, wherein therequest message comprises at least one of a UE identity, networkidentity, information indicating the radio access technology applied bythe mobile communications network, and an area identity indicating alogical or geographical region within the mobile communications network.29. The mobility node according to claim 25, wherein the one or moreprocessors are further configured to: transmit, to the policy node, asupport indication which indicates that the mobility node supportsreception and handling of the access information indicating whichgeographical areas comprised in the mobile communications network the UEis allowed or denied access to.
 30. The mobility node according to claim25, wherein the one or more processors are further configured to: whenthe access information indicates that the UE is not allowed to access ageographical area in the mobile communications network, determine thatthe UE's request to access the geographical area in the mobilecommunications network should be rejected when the access informationindicates that the UE is not allowed to access the geographical area inthe mobile communications network; and terminate the UE's sessiontowards the policy node, wherein the session is associated with accessto the region in the mobile communications network.
 31. The mobilitynode according to claim 25, wherein the access information received fromthe policy node supersedes access restriction information received fromanother subscriber database or a local configuration associated withaccess to geographical areas in the mobility node.
 32. The mobility nodeaccording to claim 25, wherein the one or more processors are furtherconfigured to: transmit an acknowledgement message to the policy node,wherein the acknowledgement message acknowledges the receipt of theaccess information.
 33. The mobility node according to claim 25, whereinthe mobile communications network is a PLMN and the access informationis per the radio access technology and per network identity.
 34. Themobility node according to claim 25, wherein the mobility node is aMobility Management Entity, MME, or a Serving General packet radioservice Support Node, SGSN, or a combined MME and SGSN node and whereinthe policy node is a Policy and Charging Rules Function, PCRF, node.